Rhapsody Developer Release Copyright 1997 by Apple Computer, Inc. All Rights Reserved.

Rhapsody Developer Release Notes:
Installation

These notes are for the Rhaspody installation process, including the installation tools that are used to boot the system from a CD, install a base system, and install packages and updates to the system.

Notes Specific to Rhapsody Developer Release

New Features

• Installer.app (in /NextAdmin) now uses the gnutar tool to create and read packages. OpenStep packages created with tools that predate the Rhapsody Developer Release do not work with the Installer application included with Rhapsody.
  
  
• BuildDisk.app (in /NextAdmin) no longer displays the percentage complete as an absurdly high number. The application also now installs on drives larger than 4 GB.
  
  
• Many of the command-line tools have been given autorelease pools, which enhances their performance.
  

Installing With installer.sh

You can install packages using installer.sh. To do this, launch the Terminal application (in /NextApps) and enter the following:

installer.sh -install packagePath destinationPath

Since some packages required a specific destination location, the script might return the error message "This package is not relocatable." If this happens, enter the command again, but without including the destination path.

You can get information on a package by entering:

installer.sh -info packagePath

To get additional information about installer.h, enter:

instsaller.sh --h

Installing "Fat" Developer Libraries

After installing the system, insert the installation CD. As root enter the following in a Terminal shell:

cd CD name/NextCD/Packages
installer.sh --verbose DeveloperLibs.pkg

The script prints out a few lines stating the status of the installation. Upon completion of the installer script, press Command-Power to get the Restart panel. Then enter "r" to reboot the system.

The reboot is necessary because the System.framework shared library changed and the system's dynamic linker has invalid offsets to the old System.framework.

Known Problems

• Free space partitions located immeadiately before the destination HFS partition for installing confuse the installer script.
  
  
• A related problem prevents installation on the last partition created on a drive formatted with LaCie SilverLining. You can either install into another HFS partition, or use SilverLining to repartition the disk so that the destination partition for installation is not the last one on the disk. Do this by splitting the last partition into two partitions, one almost the same size as the existing partition, and the second a very small partition that occupies the last spot in the partition map. You can also install onto a dedicated external drive (this is the recommended course).
  
  
• Windows only: When you run the SETUP.EXE program, make sure that there are no spaces in your PATH environment variable. If there are spaces in PATH, the SETUP program replaces the PATH variable instead of modifying it. To work around this problem, use directory names that comform to the "8.3" standard; you can find the 8.3 name of a directory in the Windows Explorer Properties panel for the directory. For example, instead of using C:\Program Files\WindowsNT you should use C:\Progra~1\WindowsNT.
  
  
• Windows only: After installing Rhapsody, ensure that there is no CLASSPATH variable defined in the System environment or in an AUTOEXEC.BAT file in the root directory of your boot drive. If you have any user-defined class paths, ensure that they are merged correctly into the CLASSPATH variable defined in the User environment.